You search for '@scalingsynthesis/q how could a graph database structure be visualized and perceived by end users in a more helpful way than a large graph'.
This you find around the Internetโฆ
๐ Results from Google โข Bing โข DDG โข Marginalia (embeds) โข Maps โข YouTube โข YouTube Music โข Spotify โข Bluesky โข Fediverse โข X
This you find in the Agora of Flanciaโฆ
๐ Node [[q how could a graph database structure be visualized and perceived by end users in a more helpful way than a large graph]] โถ subnode @scalingsynthesis/q how could a graph database structure be visualized and perceived by end users in a more helpful way than a large graph
A node contains individual contributions with filenames matching the topic of the current Agora location.
๐ content/Q- How could a graph database structure be visualized and perceived by end users in a more helpful way than a large graph.md contributed by ๐ค @scalingsynthesis ๏ธ๐ โ๏ธ
[[P- Chris Granger]] claims that showing more than 15-20 nodes at a time makes a graph view unmanageable.
[[Codex OS]] has proposed an autocomplete that prioritizes the relationships for browsing:
Expanding on that idea, I believe that, similar to Finderโs view of nested folders (Miller Columns), we could let people traverse nodeโ>edgeโ>nodeโ>edge relationships with simple arrow commands. So in the above example, it might look like you select the Michaelangelo option and it shows you the relationship options from there, you select the relationship, then select a node from within there, and onโฆ
Loose mockups below:
Loading pushes...
Rendering context...
๐ฃ๏ธ Shared spaces for [[@scalingsynthesis/q how could a graph database structure be visualized and perceived by end users in a more helpful way than a large graph]]
A stoa is a semi-public space where interested people can meet and collaborate.
x
โ Edit [[@scalingsynthesis/q how could a graph database structure be visualized and perceived by end users in a more helpful way than a large graph]] (requires sign-in)
What could we show here?